Didier Raboud [Wed, 23 May 2012 08:08:42 +0000 (10:08 +0200)]
PyUT: Implement test for lsb_release.guess_debian_release.
This includes a modification of lsb_release.py to enable an
overridability with an environment variable LSB_ETC_DEBIAN_VERSION that
can point to another /etc/debian_version.
Didier Raboud [Tue, 22 May 2012 13:19:54 +0000 (15:19 +0200)]
PyUT: Implement test for lsb_release.get_lsb_information.
This includes a modification of lsb_release.py to enable an
overridability with an environment variable LSB_ETC_LSB_RELEASE that can
point to another /etc/lsb-release
Didier Raboud [Mon, 21 May 2012 12:58:14 +0000 (14:58 +0200)]
Allow FANCYTTY to be sourced from /etc/default/rcS.
The FANCYTTY shell variable is sourced from /etc/default/rcS before
etc/lsb-base-logging.sh .
- Systems with an administrator-provided /etc/lsb-base-logging.sh keep
working.
- Systems without /etc/lsb-base-logging.sh can now override FANCYTTY in
/etc/default/rcS too.
Thanks-To: Roger Leigh <rleigh@codelibre.net> Reported-by: Stanislav Maslovski <stanislav.maslovski@gmail.com> Closes: #673207
Git-Dch: Full
Didier Raboud [Wed, 9 May 2012 12:43:17 +0000 (14:43 +0200)]
In init-functions, include hooks from other packages.
- Add a /lib/lsb/init-functions.d/ empty directory for this purpose.
- Add a lintian override for the above.
- Source any file in there.
- Document that in lsb-base.README.
Didier Raboud [Mon, 7 May 2012 17:12:27 +0000 (19:12 +0200)]
PyUT: Run tests with python3 too.
Note: This currently makes the build fail in a non-clean environment without
py3versions available. This is semi-intended and is the easiest way to have
the tests run as python3 too.
Didier Raboud [Fri, 4 May 2012 11:41:25 +0000 (13:41 +0200)]
PyUT: Add initial unittest framework, limit possible python versions to >= 2.7.
Limiting the supported python versions to >= 2.6 permits to avoid unneccessary
code to permit the use of unittest in all python 2 and 3 versions such as:
import sys
if sys.version_info[0] >= 3:
import unittest
else:
import unittest2 as unittest
python2.7 is the default version in Debian unstable since Sep 2011.
pidofproc(): Make sure to try /bin/pidof when no pidfile is specified.
Move the pidof-using block inside the conditional to have it run when we know
that the pidfile doesn't exist but before assuming that the program was indeed
using one.
Closes: #668958 Reported-by: Adrian Fita <adrian.fita@gmail.com> Signed-off-by: Didier Raboud <odyx@debian.org>
Didier Raboud [Fri, 30 Mar 2012 12:48:42 +0000 (14:48 +0200)]
Make the init.d scripts messages fancier by prepending them a [....] block.
== Implementation ==
* The logging functions assign the status block as "[....]" when
printing the log message.
Concerned functions:
- log_daemon_msg
- log_action_begin_msg
- log_begin_msg (despite not being a documented interface)
* The log message conclusion functions replace the status block by
either a green [ ok ], a yellow [warn] or a red [FAIL] by
Concerned functions:
- log_end_msg
This is implemented as _pre/_post functions.
== Documentation ==
* lsb-base.README.Debian is updated with the new _pre/_post functions.
* lsb-base.NEWS gets a new entry with information meant for experimental
users and init.d scripts maintainers.
Didier Raboud [Wed, 7 Mar 2012 12:26:01 +0000 (13:26 +0100)]
In killproc(), re-add a '--retry 5' to s-s-d when no signal is specified.
According to the letter of the LSB:
killproc:"If a signal is specified, (...) the program is sent that signal.
Otherwise, a SIGTERM followed by a SIGKILL after an unspecified
number of seconds shall be sent."
According to start-stop-daemon manpage, that's what `--retry 5` does, with `5
seconds` being the `unspecified` of LSB, hence the `--retry 5` is only added
in the case where no signal is specified.
Closes: #650584 Reported-by: Daniel Nelson <torham@connect2.com> Signed-off-by: Didier Raboud <odyx@debian.org>
Didier Raboud [Sun, 11 Mar 2012 13:59:18 +0000 (14:59 +0100)]
Fix both unused and undeclared local variables in pidofproc.
This fixes:
- one bug introduced by the fix for #327405 in 3.0-6, which stopped using the
`line` variable;
- one bug introduced in 3.2-20, which started to use the `base` variable
without declaring it in local.
Closes: #663351 Reported-by: Liu Yubao <yubao.liu@gmail.com> Signed-off-by: Didier Raboud <odyx@debian.org>
Didier Raboud [Tue, 6 Mar 2012 12:45:31 +0000 (13:45 +0100)]
Promote lsb-release to Priority: optional.
Currently, 15 packages of priority "optional" depend on lsb-release and this
promotion fixes the override disparity between the archive and the package.
Didier Raboud [Sun, 19 Feb 2012 15:31:56 +0000 (16:31 +0100)]
Upgrade to support LSB 4.1.
LSB changes:
- Bump Depends:
- on libglib2.0-0 to >= 2.12.13;
- on fontconfig to >= 2.6.0;
- on libglib2.0-0 to >= 2.12.13;
- on libatk1.0-0 to >= 1.10.3;
- on libpango1.0-0 to >= 1.10.4;
- on libgtk2.0-0 to >= 2.10.14;
- Add Depends:
- on libglu1;
- on libcairo2 to >= 1.2.0;
- on libxtst6;
- on ghostscript-cups;
- In lsb, bump lsb-printing from Suggests to Depends.
- Add the lsb-security package.
- Drop the now-obsolete lsb-qt4 package.
Debian changes:
- libgl1-mesa-glx is the first alternative for libgl1;
- Make sure all packages have ${misc:Depends}.
Till Kamppeter [Sun, 19 Feb 2012 14:52:06 +0000 (15:52 +0100)]
Add the "lsb-invalid-mta" package, with a fake sendmail.
This allows the installation of LSB packages to not pull in an MTA any more,
which once adds awkward configuration questions to the installation process
and second adds an often unnneeded daemon to the system.
projects / lsb.git / log